Task Properties: Obsolete Files

Caution:
Currently, this feature is only operational in plain Backup/Synchronization mode with local/LAN destinations (no FTP, no compression, no encryption).

This section allows you to configure the way obsolete files (deleted in Source but existing in Destination) are handled.

Here is what you can do with obsolete files:

( ) Leave in Backup - Ignore them.

( ) Delete - Permanently remove from Destination.

( ) Move to Recycle Bin - Remove, but put in the Windows Recycle Bin.

( ) Save deleted files to the same destination folder - Rename them (see below) and keep where they are.

( ) Save deleted files to a separate archive folder - Rename them (see below) and move to a designated folder.
Keep folder structure -Check this if you include subfolders in Source and want them to be mirrored in this designated archive folder.

Use the Delete or Move option if you want the destination copy to match the source exactly, with no extra files. When a file in Source is deleted, its counterpart in Destination gets deleted too. If you delete files from Source, they will be deleted from Destination the next time GrandBackup runs the Task.

Number of deleted file versions to be saved - You can specify how many, if not all, obsolete file versions you would like to keep.

( ) Save all deleted versions - Keep all obsolete file versions if you think you may still need them.

( ) Save the last ___ version(s) of deleted files - Specify the number of most recent obsolete files to be saved.

GrandBackup will rename obsolete files as follows. "FileName.TXT", for example, will be named "FileName (Obsolete 2001-11-04 19-11-33).TXT", "FileName (Obsolete 2001-11-04 21-12-12).TXT" and so on (the 14 digits here represent the current date and time calculated to the second).